fix(next): fix hmr, bump minimum required next.js 16 version to 16.2.2#16202
fix(next): fix hmr, bump minimum required next.js 16 version to 16.2.2#16202DanRibbens merged 7 commits intomainfrom
Conversation
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
|
🚀 This is included in version v3.82.0 |
|
Running payload with the latest version resulting in invalid key: Edit: After looking into that Next.js' PR, I think there are inconsistencies between the PR description and the code changes. In the PR description it says |
- bumps templates to Payload 3.82.0 - removes the --no-server-fast-refresh flag from templates dev script, as [it is no longer needed with Payload 3.82.0 and Next.js 16.2.2](#16202) --- - To see the specific tasks where the Asana app for GitHub is being used, see below: - https://app.asana.com/0/0/1213983836266021
|
I suggest adding "create test instance" + "does it run without any warning or error" inside the CI scripts to prevent such issues in the future. |
payloadcms#16202) Next.js <16.2.2 requires the `--no-server-fast-refresh` flag appended to the `next dev` command in order for HMR to work. In 16.2.2, we can now set `experimental.enableServerFastRefresh` to disable server fast refresh, which fixes HMR for all users, without requiring a new flag. This PR: - bumps the minimum required Next.js 16 version to 16.2.2 - sets `experimental.enableServerFastRefresh` if Next.js >=16.2.2 is detected - bumps Next.js to 16.2.2 in our monorepo and all templates - logs a console warning for all users using Next.js 16 - 16.2.1 After release, we'll remove the `--no-server-fast-refresh` flag from our templates in a separate PR. We cannot do it in this PR, as a newer Payload version is required --- - To see the specific tasks where the Asana app for GitHub is being used, see below: - https://app.asana.com/0/0/1213971891044433
…oadcms#16212) - bumps templates to Payload 3.82.0 - removes the --no-server-fast-refresh flag from templates dev script, as [it is no longer needed with Payload 3.82.0 and Next.js 16.2.2](payloadcms#16202) --- - To see the specific tasks where the Asana app for GitHub is being used, see below: - https://app.asana.com/0/0/1213983836266021

Next.js <16.2.2 requires the
--no-server-fast-refreshflag appended to thenext devcommand in order for HMR to work. In 16.2.2, we can now setexperimental.enableServerFastRefreshto disable server fast refresh, which fixes HMR for all users, without requiring a new flag.This PR:
experimental.enableServerFastRefreshif Next.js >=16.2.2 is detectedAfter release, we'll remove the
--no-server-fast-refreshflag from our templates in a separate PR. We cannot do it in this PR, as a newer Payload version is required